Method and apparatus for white space operation by a mobile entity

ABSTRACT

A method by an access point for wireless communication service includes receiving configuration parameters from a core network entity for operation as a base station using at least one non-white space (non-WS) bandwidth. The method further includes determining whether the received configuration parameters comprise an indication for the access point to use white space (WS) for the service. The method further includes requesting authorization information from a WS database to operate in the WS, in response to the received parameters comprising the indication. An access point comprising a processor, memory and transceiver may be configured to perform the elements of the method, using a computer-readable storage medium or other means.

CROSS-REFERENCE TO RELATED APPLICATION

The present Application for Patent claims priority to ProvisionalApplication No. 61/593,792, filed Feb. 1, 2012, entitled “METHOD ANDAPPARATUS FOR WHITE SPACE OPERATION BY A MOBILE ENTITY”, whichapplication is assigned to the assignee hereof, and expresslyincorporated in its entirety by reference herein.

BACKGROUND

1. Field

The present disclosure relates to wireless communication systems, andmore particularly, to white space (WS) techniques in Long Term Evolution(LTE) systems.

2. Background

Wireless communication systems are widely deployed to provide varioustypes of communication content such as voice, data, video and the like,and deployments are likely to increase with introduction of new dataoriented systems, such as Long Term Evolution (LTE) systems. Wirelesscommunications systems may be multiple-access systems capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., bandwidth and transmit power). Examples of suchmultiple-access systems include code division multiple access (CDMA)systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, 3GPP LTE systems and otherorthogonal frequency division multiple access (OFDMA) systems.

3GPP LTE represents a major advance in cellular technology as anevolution of Global System for Mobile communications (GSM) and UniversalMobile Telecommunications System (UMTS). The LTE physical layer (PHY)provides a highly efficient way to convey both data and controlinformation between base stations, such as an evolved Node Bs (eNBs),and mobile entities.

An orthogonal frequency division multiplex (OFDM) communication systemeffectively partitions the overall system bandwidth into multiple(N_(F)) subcarriers, which may also be referred to as frequencysub-channels, tones, or frequency bins. For an OFDM system, the data tobe transmitted (i.e., the information bits) is first encoded with aparticular coding scheme to generate coded bits, and the coded bits arefurther grouped into multi-bit symbols that are then mapped tomodulation symbols. Each modulation symbol corresponds to a point in asignal constellation defined by a particular modulation scheme (e.g.,M-PSK or M-QAM) used for data transmission. At each time interval thatmay be dependent on the bandwidth of each frequency subcarrier, amodulation symbol may be transmitted on each of the N_(F) frequencysubcarrier. Thus, OFDM may be used to combat inter-symbol interference(ISI) caused by frequency selective fading, which is characterized bydifferent amounts of attenuation across the system bandwidth.

Generally, a wireless multiple-access communication system cansimultaneously support communication for a number of mobile entities,such as, for example, user equipments (UEs) or access terminals (ATs). AUE may communicate with a base station via the downlink and uplink. Thedownlink (or forward link) refers to the communication link from thebase station to the UE, and the uplink (or reverse link) refers to thecommunication link from the UE to the base station. Such communicationlinks may be established via a single-in-single-out,multiple-in-signal-out, or a multiple-in-multiple-out (MIMO) system.

As the number of entities deployed increases, the need for properbandwidth utilization on licensed as well as RF spectrum for which thecellular operator is not licensed or holds only a secondary license,including whitespace spectrum, becomes more important. In the context ofcognitive radio networks, certain frequency bands may be underutilizedby an incumbent primary licensee. Such frequency bands may be madeavailable to secondary users (e.g. cellular operators) when the primaryuser is not active. Due to changes in primary and/or secondary useractivity, changing the operating spectrum for the secondary licenseesmay be necessary. In this context, there remains a need for efficientauthentication and authorization of wireless devices serviced bycellular operators in cognitive LTE networks and/or similar wirelesscommunication networks.

SUMMARY

Methods, apparatus and systems for wireless communication service usingwhitespace spectrum are described in detail in the detailed description,and certain aspects are summarized below. This summary and the followingdetailed description should be interpreted as complementary parts of anintegrated disclosure, which parts may include redundant subject matterand/or supplemental subject matter. An omission in either section doesnot indicate priority or relative importance of any element described inthe integrated application. Differences between the sections may includesupplemental disclosures of alternative embodiments, additional details,or alternative descriptions of identical embodiments using differentterminology, as should be apparent from the respective disclosures.

In an aspect, a method operable by an access point for wirelesscommunication service may include receiving configuration parametersfrom a core network entity for operation as a base station using atleast one non-white space (non-WS) bandwidth. In an aspect, theconfiguration parameters may include an indication to use white spacefor a backhaul or an access connectivity. The base station may be, ormay include, a macrocell eNB, a femtocell, a picocell, or a UE eNB, andmay operate in at least one whitespace (WS) radio band and at least onenon-WS radio band (i.e., in both WS and non-WS). The base station may beoperated by a primary licensee of the at least one non-WS band, who is asecondary licensee of the at least one WS band. The access point mayoperate in a cognitive LTE network.

The method may further include determining, at the access point, whetherthe received configuration parameters comprise an indication for theaccess point to use white space (WS) for the service. In an aspect, theindication may include an information element (IE) indicating that theaccess point should use the WS. In an alternative aspect, the indicationmay include a list of bands for the operation, wherein at least one bandin the list is a WS band.

The method may further include requesting authorization information froma WS database to operate in the WS, in response to the receivedparameters comprising the indication. The received parameters mayinclude an identifier for the at least one WS band, which the accesspoint may transmit for requesting the authorization information. The WSdatabase may be operated by a network entity.

The access point may receive the requested authorization informationfrom the network entity. The authorization information may indicatewhether or not the access point is authorized to use one or more WSbands for which the access point has received configuration parametersand/or requested authorization. In addition, the configurationparameters for different WS bands may permit discrimination between WSbands for a wireless communication service to be required by the accesspoint. Accordingly, the method may include the access point selecting aWS channel based on at least one of the configuration parameters and theauthorization information.

In other, more detailed aspects, requesting the authorizationinformation may include the access point requesting to operate as amaster WS device (WSD). In the alternative, requesting the authorizationinformation may include the access point requesting to operate as aslave WS device (WSD). For example, requesting the authorizationinformation may include the access point requesting to operate as aslave WSD in response to the indication to use white space for thebackhaul connectivity. For further example, requesting the authorizationinformation may include the access point requesting to operate as amaster WSD in response to the indication to use white space for theaccess connectivity. Configurations for slave and master WSDs may be asknown in the art. In another more detailed aspect, the method mayinclude the access point authorizing a slave WSD for use of the WS.

In related aspects, a wireless communication apparatus may be providedfor performing any of the methods and aspects of the methods summarizedabove. An apparatus may include, for example, a processor coupled to amemory, wherein the memory holds instructions for execution by theprocessor to cause the apparatus to perform operations as describedabove. Certain aspects of such apparatus (e.g., hardware aspects) may beexemplified by equipment such as an access point, for example a basestation, eNB, macrocell, femtocell, or the like. Similarly, an articleof manufacture may be provided, including a computer-readable storagemedium holding encoded instructions, which when executed by a processor,cause a computer to perform the methods and aspects of the methods assummarized above.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram conceptually illustrating an example of atelecommunications system.

FIG. 2 illustrates details of a wireless communications system includingan evolved Node B (eNB) and multiple user equipments (UEs).

FIG. 3 illustrates a cognitive radio system using white space (WS).

FIG. 4 illustrates an implementation of a cognitive Long Term Evolution(LTE) system with a closed subscriber group (CSG) femtocell.

FIG. 5 illustrates details of an embodiment of signaling using a WS anda licensed channel.

FIG. 6 illustrates an embodiment of a SIB for use in cognitive LTE.

FIG. 7 illustrates an eNB configuration using multiple downlink (DL)channels.

FIG. 8 illustrates a DL channelization for one embodiment of licensed toWS DL transition.

FIG. 9 illustrates a DL channelization for one embodiment of licensed toWS DL transition.

FIG. 10 illustrates an embodiment of a process for UE connection to aneNB.

FIG. 11 illustrates an embodiment of a process for interferencecoordination in a cognitive LTE network.

FIG. 12 illustrates an embodiment of a process for interferencecoordination in a cognitive LTE network.

FIG. 13 illustrates details an embodiment of a cognitive networkincluding a UE and eNB which may be WS-enabled.

FIGS. 14A-B show embodiments of a UE eNodeB (UeNB) providing networkconnectivity to a terminal UE over a wired backhaul and an LTE backhaul.

FIG. 15 shows an example architecture reference model for a UeNB.

FIG. 16 shows an example architecture reference model for a UeNB actingas a relay.

FIG. 17 illustrates an example call flow for UeNB setup for WS backhaul.

FIG. 18 illustrates an example call flow for UeNB setup for WS access.

FIG. 19 shows an example architecture reference model for white spaceoperation.

FIG. 20 provides a call flow for an embodiment of WS initialauthorization for the slave WSD.

FIG. 21 provides a call flow for another embodiment of WS initialauthorization for the slave WSD.

FIG. 22 illustrates an example call flow for WS continued authorizationfor the slave WSD.

FIG. 23 illustrates an example master WSD setup methodology executableby a UeNB or the like.

FIG. 24 illustrates further aspects of the methodology of FIG. 23.

FIG. 25 shows an embodiment of an apparatus for master WSD setup, inaccordance with the methodology of FIG. 23.

DETAILED DESCRIPTION

Techniques for supporting cognitive radio communication are describedherein. The techniques may be used for various wireless communicationnetworks such as wireless wide area networks (WWANs) and wireless localarea networks (WLANs). The terms “network” and “system” are often usedinterchangeably. The WWANs may be CDMA, TDMA, FDMA, OFDMA, SC-FDMAand/or other networks. A CDMA network may implement a radio technologysuch as, for example, Universal Terrestrial Radio Access (UTRA) orcdma2000. UTRA includes Wideband CDMA (WCDMA) and other variants ofCDMA, while cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMAnetwork may implement a radio technology such as Global System forMobile Communications (GSM). An OFDMA network may implement a radiotechnology such as, for example, Evolved UTRA (E-UTRA), Ultra MobileBroadband (UMB), IEEE 802.16 (WiMAX), IEEE 802.20, or Flash-OFDM®. UTRAand E-UTRA are part of Universal Mobile Telecommunication System (UMTS).3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releasesof UMTS that use E-UTRA, which employs OFDMA on the downlink and SC-FDMAon the uplink. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described indocuments from an organization named “3rd Generation PartnershipProject” (3GPP). UMB and cdma2000 are described in documents from anorganization named “3rd Generation Partnership Project 2” (3GPP2). AWLAN may implement a radio technology such as, for example, IEEE 802.11(Wi-Fi), or HiperLAN.

The techniques described herein may be used for the wireless networksand radio technologies mentioned above as well as other wirelessnetworks and radio technologies. For clarity, certain aspects of thetechniques are described below for 3GPP network and WLAN, and LTE andWLAN terminology is used in much of the description below.

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that the variousaspects may be practiced without these specific details. In otherinstances, well-known structures and devices are shown in block diagramform in order to facilitate describing these aspects.

FIG. 1 shows a wireless communication network 10, which may be an LTEnetwork or some other wireless network. Wireless network 10 may includea number of evolved Node Bs (eNBs) 30 and other network entities. An eNBmay be an entity that communicates with mobile entities (e.g., userequipment (UE)) and may also be referred to as a base station, a Node B,a macrocell, an access point, or other terminology. Although the eNBtypically has more functionalities than a base station, the terms “eNB”and “base station” are used interchangeably herein. Each eNB 30 mayprovide communication coverage for a particular geographic area and maysupport communication for mobile entities (e.g., UEs) located within thecoverage area. To improve network capacity, the overall coverage area ofan eNB may be partitioned into multiple (e.g., three) smaller areas.Each smaller area may be served by a respective eNB subsystem. In 3GPP,the term “cell” can refer to the smallest coverage area of an eNB and/oran eNB subsystem serving this coverage area, depending on the context inwhich the term is used.

An eNB may provide communication coverage for a macrocell, a picocell, afemtocell, and/or other types of cell. A macrocell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femtocell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femtocell (e.g.,UEs in a Closed Subscriber Group (CSG)). In the example shown in FIG.1A, eNBs 30 a, 30 b, and 30 c may be macro eNBs for macrocell groups 20a, 20 b, and 20 c, respectively. Each of the cell groups 20 a, 20 b, and20 c may include a plurality (e.g., three) of cells or sectors. An eNB30 d may be a pico eNB for a pico cell 20 d. An eNB 30 e may be a femtoeNB or femto access point (FAP) for a femtocell 20 e.

Wireless network 10 may also include relays (not shown in FIG. 1A). Arelay may be an entity that can receive a transmission of data from anupstream station (e.g., an eNB or a UE) and send a transmission of thedata to a downstream station (e.g., a UE or an eNB). A relay may also bea UE that can relay transmissions for other UEs.

A network controller 50 may couple to a set of eNBs and may providecoordination and control for these eNBs. Network controller 50 may be asingle network entity or a collection of network entities. Networkcontroller 50 may communicate with the eNBs via a backhaul. The eNBs mayalso communicate with one another, e.g., directly or indirectly via awireless or wireline backhaul.

UEs 40 may be dispersed throughout wireless network 10, and each UE maybe stationary or mobile. A UE may also be referred to as a mobilestation, a terminal, an access terminal, a subscriber unit, a station,or other terminology. A UE may be a cellular phone, a personal digitalassistant (PDA), a wireless modem, a wireless communication device, ahandheld device, a laptop computer, a cordless phone, a wireless localloop (WLL) station, a smart phone, a netbook, a smartbook, or otherclient device. A UE may be able to communicate with eNBs, relays, andother access points or network wireless nodes. A UE may also be able tocommunicate peer-to-peer (P2P) with other UEs.

Wireless network 10 may support operation on a single carrier ormultiple carriers for each of the downlink (DL) and uplink (UL). Acarrier may refer to a range of frequencies used for communication andmay be associated with certain characteristics. Operation on multiplecarriers may also be referred to as multi-carrier operation or carrieraggregation. A UE may operate on one or more carriers for the DL (or DLcarriers) and one or more carriers for the UL (or UL carriers) forcommunication with an eNB. The eNB may send data and control informationon one or more DL carriers to the UE. The UE may send data and controlinformation on one or more UL carriers to the eNB. In one design, the DLcarriers may be paired with the UL carriers. In this design, controlinformation to support data transmission on a given DL carrier may besent on that DL carrier and an associated UL carrier. Similarly, controlinformation to support data transmission on a given UL carrier may besent on that UL carrier and an associated DL carrier. In another design,cross-carrier control may be supported. In this design, controlinformation to support data transmission on a given DL carrier may besent on another DL carrier (e.g., a base carrier) instead of the DLcarrier.

Wireless network 10 may support carrier extension for a given carrier.For carrier extension, different system bandwidths may be supported fordifferent UEs on a carrier. For example, the wireless network maysupport (i) a first system bandwidth on a DL carrier for first UEs(e.g., UEs supporting LTE Release 8 or 9 or some other release) and (ii)a second system bandwidth on the DL carrier for second UEs (e.g., UEssupporting a later LTE release). The second system bandwidth maycompletely or partially overlap the first system bandwidth. For example,the second system bandwidth may include the first system bandwidth andadditional bandwidth at one or both ends of the first system bandwidth.The additional system bandwidth may be used to send data and possiblycontrol information to the second UEs.

Wireless network 10 may support data transmission via single-inputsingle-output (SISO), single-input multiple-output (SIMO),multiple-input single-output (MISO), and/or multiple-inputmultiple-output (MIMO). For MIMO, a transmitter (e.g., an eNB) maytransmit data from multiple transmit antennas to multiple receiveantennas at a receiver (e.g., a UE). MIMO may be used to improvereliability (e.g., by transmitting the same data from differentantennas) and/or to improve throughput (e.g., by transmitting differentdata from different antennas).

Wireless network 10 may support single-user (SU) MIMO, multi-user (MU)MIMO, Coordinated Multi-Point (CoMP), or similar technology. ForSU-MIMO, a cell may transmit multiple data streams to a single UE on agiven time-frequency resource with or without precoding. For MU-MIMO, acell may transmit multiple data streams to multiple UEs (e.g., one datastream to each UE) on the same time-frequency resource with or withoutprecoding. CoMP may include cooperative transmission and/or jointprocessing. For cooperative transmission, multiple cells may transmitone or more data streams to a single UE on a given time-frequencyresource such that the data transmission is steered toward the intendedUE and/or away from one or more interfered UEs. For joint processing,multiple cells may transmit multiple data streams to multiple UEs (e.g.,one data stream to each UE) on the same time-frequency resource with orwithout precoding.

Wireless network 10 may support hybrid automatic retransmission (HARQ)in order to improve reliability of data transmission. For HARQ, atransmitter (e.g., an eNB) may send a transmission of a data packet (ortransport block) and may send one or more additional transmissions, ifneeded, until the packet is decoded correctly by a receiver (e.g., aUE), or the maximum number of transmissions has been sent, or some othertermination condition is encountered. The transmitter may thus send avariable number of transmissions of the packet.

Wireless network 10 may support synchronous or asynchronous operation.For synchronous operation, the eNBs may have similar frame timing, andtransmissions from different eNBs may be approximately aligned in time.For asynchronous operation, the eNBs may have different frame timing,and transmissions from different eNBs may not be aligned in time.

Wireless network 10 may utilize frequency division duplex (FDD) or timedivision duplex (TDD). For FDD, the DL and UL may be allocated separatefrequency channels, and DL transmissions and UL transmissions may besent concurrently on the two frequency channels. For TDD, the DL and ULmay share the same frequency channel, and DL and UL transmissions may besent on the same frequency channel in different time periods. In relatedaspects, the FAP synchronization process described in further detailbelow may be applied to the FAPs using FDD or TDD duplexing.

Referring now to FIG. 2, a multiple access wireless communication systemaccording to one aspect is illustrated. An access point or eNB 200includes multiple antenna groups, one including 204 and 206, anotherincluding 208 and 210, and an additional including 212 and 214. In FIG.2, only two antennas are shown for each antenna group, however, more orfewer antennas may be utilized for each antenna group. Access terminalor UE 216 is in communication with antennas 212 and 214, where antennas212 and 214 transmit information to access terminal 216 over forwardlink 220 and receive information from access terminal 216 over reverselink 218. Access terminal 222 is in communication with antennas 206 and208, where antennas 206 and 208 transmit information to access terminal222 over forward link 226 and receive information from access terminal222 over reverse link 224. In a FDD system, communication links 218,220, 224 and 226 may use different frequencies for communication. Forexample, forward link 220 may use a different frequency then that usedby reverse link 218.

Each group of antennas and/or the area in which they are designed tocommunicate is often referred to as a sector of the access point.Antenna groups each are designed to communicate to access terminals in asector, of the areas covered by access point 200. In communication overforward links 220 and 226, the transmitting antennas of access point 200may utilize beamforming in order to improve the signal-to-noise ratio offorward links for the different access terminals 216 and 224. Also, anaccess point using beam-forming to transmit to access terminalsscattered randomly through its coverage causes less interference toaccess terminals in neighboring cells than an access point transmittingthrough a single antenna to all its access terminals. An access pointmay be a fixed station used for communicating with the terminals and mayalso be referred to as an access point, a Node B, evolved Node B (eNB)or some other terminology. An access terminal may also be called anaccess terminal, user equipment (UE), a wireless communication device,terminal, access terminal or some other terminology.

In accordance with aspects of the subject of this disclosure, cognitiveradio refers generally to wireless communication systems where either awireless network or network node includes intelligence to adjust andchange transmission and/or reception parameters to provide efficientcommunication, while avoiding interference with other licensed orunlicensed users. Implementation of this approach includes activemonitoring and sensing of the operational radio environment, which mayinclude frequency spectrum, modulation characteristics, user behavior,network state, and/or other parameters. Multiple-access systems, such asLTE and LTE-A systems, may use cognitive radio techniques to utilizeadditional available spectrum beyond the specifically licensed spectrum.

Spectrum sensing involves detection of potentially usable spectrum. Onceusable spectrum is detected, it may then be used either alone (ifunoccupied) or shared, assuming other users are present, without causingharmful interference. Nodes in cognitive radio systems may be configuredto sense spectrum holes, which may be based on detecting primary users(such as, for example, licensed users of the shared spectrum), or otherusers (such as, for example, unlicensed users). Once usable spectrum isselected, it may then be further monitored to detect use by others. Forother higher priority users, the spectrum may need to vacated andcommunications transferred to other channels. For example, if a primaryuser is detected during initial search, an unlicensed user may beprohibited from using the spectrum. Likewise, if a primary user appearsin spectrum being used by an unlicensed user, the unlicensed user mayneed to vacate.

Spectrum sensing techniques can include transmitter detection, wherecognitive radio nodes have the capability to determine if a signal froma primary user is locally present in a certain spectrum. This may bedone by techniques such as matched filter/correlation detection, energyor signal level detection, cyclo-stationary feature detection, or othertechniques. A primary user may be a higher priority user, such as alicensed user of shared spectrum which unlicensed users may also use.

Cooperative detection may also be used in some cases where multiplenetwork nodes are in communication. This approach relates to spectrumsensing methods where information from multiple cognitive radio usersare incorporated for primary user detection. Interference-based, orother detection methods may likewise be used to sense availablespectrum.

Cognitive radio systems generally include functionality to determine thebest available spectrum to meet user and/or network communicationrequirements. For example, cognitive radios may decide on the bestspectrum band to meet specific Quality of Service (QOS), data raterequirements, or other requirements over available spectrum bands. Thisrequires associated spectrum management and control functions, which mayinclude spectrum analysis as well as spectrum decision processing toselect and allocate available spectrum.

Because the spectrum is typically shared, spectrum mobility is also aconcern. Spectrum mobility relates to a cognitive network user changingoperational frequency. This is generally done in a dynamic manner byallowing network nodes to operate in the best available frequency band,and maintaining seamless communications during the transition toother/better spectrum. Spectrum sharing relates to providing a fairspectrum scheduling method, which can be regarded as similar to genericmedia access control (MAC) problems in existing networks.

One aspect of cognitive radio relates to sharing use of licensedspectrum by unlicensed users. Use of this spectrum may be integratedwith other wireless communication methodologies, such as LTE.

White space (WS) refers to frequencies allocated to a broadcastingservice or other licensed user that are not used locally, as well as tointerstitial bands. In the United States, the switchover to digitaltelevision in 2009 created abandoned spectrum in the upper 700 megahertzband (698 to 806 MHz), and additional WS is present at 54-698 MHz (TVChannels 2-51) which is still in use for digital television. Incumbentprimary users may include licensed television broadcasters on existingchannels, wireless microphone systems, medical devices, or other legacydevices. In 2008, the United States Federal Communications Commission(FCC) approved unlicensed use of this WS. However, these so-called “TVBand Devices,” must operate in the vacant channels or WSs betweentelevision channels in the range of 54 to 698 MHz.

Rules defining these devices were published by the U.S. FCC in a SecondReport and Order on Nov. 14, 2008. The FCC rules define fixed andpersonal/portable devices. Fixed devices may use any of the vacant US TVchannels 2, 5-36 and 38-51 with a power of up to 1 watt (4 watts EIRP).They may communicate with each other on any of these channels, and alsowith personal/portable devices in the TV channels 21 through 51. Fixeddevices must be location-aware, query an FCC-mandated database at leastdaily to retrieve a list of usable channels at their location, and mustalso monitor the spectrum locally once every minute to confirm that nolegacy wireless microphones, video assist devices, or other emitters arepresent. If a single transmission is detected, the device may nottransmit anywhere within the entire 6 MHz channel in which thetransmission was received. Fixed devices may transmit only within the TVchannels where both the database indicates operation is permissible, andno signals are detected locally.

Personal/portable stations may operate only on channels 21-36 and 38-51,with a power of 100 mW EIRP, or 40 mW if on a channel adjacent to anearby television channel. They may either retrieve a list ofpermissible channels from an associated fixed station, or may accept alower output power of 50 mW EIRP and use only spectrum sensing.

As noted previously, existing wireless networks may be enhanced byaddition of cognitive radio functionality. In one aspect, an LTE systemmay include cognitive radio functionality as further illustrated below.

Attention is now directed to FIG. 3, which illustrates an example of acognitive LTE system 300 configured to utilize WS, such as in the UHFtelevision spectrum. A first cell 303 is configured to utilize WS on oneor both of the DL and UL. In one implementation, licensed spectrum isused for the UL, while WS may be used for the DL for certaincommunications. For example, a WS-enabled eNB 310 may be incommunication with a first UE 316 as well as a second UE 314. UE 316 maybe a non-WS enabled UE, whereas UE 314 may be WS-enabled. (as usedherein, WS-enabled refers to a network device configured to utilize WS,typically in addition to licensed spectrum). In the example, DL 317 andUL 318, between eNB 310 and UE 316, are configured to use licensedspectrum, whereas DL 312, between eNB 310 and UE 314, may be configuredto use WS, while UL 313 may be configured to use licensed spectrum.

Another cell 305 may be adjacent to cell 303 and may be configured withan eNB 330 to communicate with UE 332 using licensed spectrum for DL 333and UL 334. In some situations, UE 314 may be within range of eNB 330and as such may be subject to attempts by UE 314 to access eNB 330.

As noted previously, use of WS by devices in cognitive networks requiressensing of channel conditions. In systems such as LTE systems configuredto operate in TV band WS, FCC requirements mandate monitoring thespectrum being utilized by a secondary device (i.e., a non-licenseduser) for primary uses and vacation of the channel if a primary user isdetected. Typical primary uses may be UHF television channels, wirelessmicrophones, or other legacy devices.

In addition, coordination with other secondary users may be desirable tofacilitate frequency sharing. FCC requirements mandate checking thechannel for 30 second before switching to a new channel, monitoringchannels at least every 60 seconds for primary users, and vacating thechannel within 2 second when a primary user is detected. Duringchecking, a quiet period is required in which no signal transmission ofany network device is done. For example, in an LTE network having an eNBand three associated UEs, all four of these devices must refrain fromtransmitting during the quiet period so that other users may bedetected.

FIG. 4 illustrates an example cognitive LTE system 400 including cell401, which may be a macrocell, having associated eNB 410, which may beWS-enabled. In some implementations, cell 401 may be a femtocell orpicocell, however, for purposes of illustration, FIG. 4 is describedbased on the assumption that cell 401 is a macrocell having a rangeincluding at least the distance to UE 420 as shown. UE 420 may be aWS-enabled UE, which may be capable of communicating as a legacy UEand/or as a WS-UE. An additional cell 403 may be in proximity to UE 420.eNB 430, which may be a femtonode, may be associated with cell 403, andmay be in communication with one or more additional UEs (UE 440, andother UEs not shown). UE 420 may be in close proximity to eNB 430 and/ormay receive a stronger signal from eNB 430 than from eNB 410. Ingeneral, UE 420 may seek to connect with eNB 430; however, eNB 430 maybe part of a closed subscriber group (CSG) or may otherwise allow onlyrestricted access. Consequently, UE 420 may establish a connection witheNB 410, such as via DL 417 and UL 418, as shown. Interference 432 maybe generated by eNB 430 and may constrain operation of UE 420,particularly if the transmit signal levels from eNB 410 are weakrelative to those from eNB 430. Additional UL interference 434 may begenerated by UE 420, which may interfere with operation of cell 403.Consequently, it may be desirable for UE 420 to communicate with eNB 410primarily on one or more WS channels (not shown), rather than onlicensed channels. This may be done by limiting the signaling providedon licensed channels, such as to limit signaling to synchronizationand/or broadcast information. In particular, this may be important on alicensed DL such as DL 417 shown in FIG. 4. In addition to thisscenario, other network configurations may also make it desirable tolimit communications between eNBs and UEs on licensed channels.

In order to address these problems, as well as others, operation betweenWS-enabled eNBs and UEs may be performed such that some or most of thetraffic, particularly on the DL, is done using WS channels. In someimplementations, only synchronization and control data and informationmay be provided on a licensed DL channel, while other data andinformation may be provided on one or more WS channels. In someimplementations, modifications may be made to accommodate bothWS-enabled and legacy (i.e., non-WS), UEs when connecting to aWS-enabled eNB. In cases using only WS-enabled UEs, use of licensedspectrum may be completely eliminated; however, in order to supportlegacy UE functionality, some licensed channel functionality isgenerally needed.

Attention is now directed to FIG. 5, which illustrates a cognitive LTEsystem 500 including an eNB 510, which may be WS-enabled, and a UE 520,which may also be WS-enabled. Other cell nodes, as well as adjacentcells and their nodes (not shown) may also be present. Network 500 maybe a heterogeneous network deployment, supporting different cells andnodes. These cells and nodes may be macrocells and corresponding nodes(which may be, for example, conventional base stations that usededicated backhaul and are open to public access, with typical transmitpower of approximately 43 dBm and antenna gain of 12-15 dBi), picocellsand corresponding nodes (e.g., low power base stations that usededicated backhaul connections and are open to public access, withtypical transmit power of approximately 23-30 dBm and antenna gain of0-5 dBi), femtocells and corresponding nodes (e.g., consumer deployablebase stations that use a consumer's broadband connection for backhauland may have restricted access, with typical transmit power less than 23dBm) and/or relays (e.g. base stations using the same spectrum asbackhaul and access, having power levels similar to picocells).

In accordance with one aspect associated with WS transmission, eNB 510may be configured so as to provide multiple DL transmissions to UE 520.As shown in FIG. 5, these may include one or more WS DL channels,including DL1 516, as well as one or more licensed DL channels DL2. DL1may be used for most of the DL transmissions between eNB 510 and UE 520,with DL2 reserved for only certain functions. These functions may be,for example, synchronization and broadcast functions, which may beprovided in a standard format for legacy UEs. Alternately, or inaddition, synchronization and broadcast signaling may also includespecific signaling for WS-UEs to facilitate operation on one or more WSchannels.

In LTE, system information on the transport side is logically mapped tothe broadcast channel (BCH), broadcast control channel (BCCH), or DLshared channel (SL-SCH). Different physical channels may be used.

In operation, a UE entering a cell will first synchronize (using, forexample, PSS and SSS) with the cell's eNB, and then once synchronizedreceive broadcast information about the cell configuration (using, forexample, the MIB and SIBs). In LTE a master information block (MIB) andsystem information blocks (SIBs) are used as part of radio resourcecontrol (RRC). The MIB includes a limited amount of informationcomprising the most frequently transmitted parameters which areessential to a UEs initial access to the network. SIB 1 containsparameters needed to determine if a cell is suitable for cell selection,as well as information about the time-domain scheduling of the othereNBs. SIB2 includes common and shared channel information. SIBS3-8include parameters used to control infra-frequency, inter-frequency, andinter-RAT (Radio Access Technology) cell reselection. Additionalinformation may also be added to SIB, including information as describedfurther herein, in various embodiments.

Once the UE has achieved synchronization, it will read the MIB to campon the cell. Since the MIB contains very little information (i.e.,information about the cell bandwidth, some information about thephysical HARQ indicator channel (PHICH), and the system frame number(SFN)).

The SIBs may be transmitted on DL-SCH mapped on PDSCH. To receiveinformation about SIB's the UE needs information about PHICH, which isread from the MIB. The BCH channel has a TTI of 40 ms, and has a verysmall transport block size, while being protected with ⅓ convolutionalcode and 16 bit CRC. This helps to keep the overhead in an LTE system toa minimum.

In order to facilitate WS operation, in one implementation, alternateSIB configurations may be used. FIG. 6 illustrates one embodiment 600 ofsuch a SIB configuration, where legacy SIB information 610, such as, forexample, was described above, may be combined with WS-specificinformation elements (IEs) 620. These WS IEs may include informationsuch as WS channel or channels information or data, WS channel priorityinformation or data, or other WS-specific data or information. TheWS-specific information may be incorporated in various SIBs, however, itmay be desirable to include the information in the most frequently sentSIBs. For example, SIBs 1 and 2 may be preferable. In someimplementations, additional control information related to cognitiveoperation may be provided. For example, control information related toquiet periods (i.e., used by UEs or other network nodes for sensing asdescribed previously), cognitive capabilities at the eNB side, such as,for example, band support, support for distributed sensing processeswherein sensing is performed at multiple network nodes and combined.Other information related to control and cognitive processing may alsobe provided in various implementations.

Attention is now directed to FIG. 7, which illustrates a WS-enabled eNBhaving multiple DL transmitters 7101 thru 710N. Each of transmitters 710may be configured to operate on a selected WS or licensed channel. At aminimum, two channels may be provided, with one being configured to uselicensed spectrum and the second being configured for WS spectrum.

In many implementations, it is expected that a UE will need to searchmany potentially available WS channels during initial cell acquisition.This may create considerable limitations in acquisition since the UEwould need to search PSS, SSS, PBCH, or other channel for each WSchannel, which may take significant time.

Consequently, rather than performing a blind search on a potentiallylarge number of WS channels, it may be desirable for the UE to performinitial acquisition using a licensed channel, and then transfer some orall operation to one or more WS channels. This approach may speed upconnection time and/or reduce overhead and/or UE power consumption.

Attention is now directed to FIG. 8, which illustrates one embodiment ofa WS-enabled system 800 on which such as process may be implemented.System 800 includes WS-enabled eNB 810 and UE 820, and may include othernodes (not shown). eNB 810 may be configured to operate on one or moreWS channels with corresponding WS transmitters 812 and 814 (it is notedthat in some implementations a single WS transmitter 812 may also beused). In addition, eNB 810 is configured to operate on at least onelicensed channel using transmitter 818.

Likewise, UE 820 may be configured with a WS receiver module 822 and aLicensed receiver module 824. In some implementations, other receivermodules (not shown) may also be used. Alternately or in addition, insome implementations receiver functionality associated with 2 or moremodules may be incorporated into a single receiver module.

In operation, UE 820 initially connects to eNB 810 by receiving signalson DL3 (on the licensed channel). This information may be limited tosynchronization and/or broadcast information, such as describedpreviously herein. Upon acquisition, UE 820 may then receive informationon one or more SIBs to facilitate transition to one or more WS channels.This information may be provided in an IE in SIBs 1 or 2, for example.These WS channels may then be searched and acquired without the need toperform extensive WS channel searching. In some cases, a single WSchannel (such as, for example, is provided via DL1 of FIG. 8).Alternately, in some implementations, multiple WS channels may be used.A second WS channel may be provided via DL2 as shown in FIG. 8).Additional WS channels (not shown) may also be provided.

In some implementations using multiple WS channels, the SIB informationprovided on the licensed channel may also include information associatedwith WS channel prioritization. For example, where multiple WS channelsare used, they may be prioritized by the eNB scheduler and/or theassociated core network. This may be based on channel characteristics,loading, or other factors such as, for example presence of primaryusers. Based on the priority, a UE may then select an appropriate WSchannel and transfer operation to that channel. As noted previously, WSoperation will generally be used primarily for the DL, however, in someimplementations WS channels may also be used for UL transmission.

In the example configuration of FIG. 8, the WS channels may be furtherorganized by functionality. For example, one WS channel may beconfigured for initial access, such as to perform random access channel(RACH) procedures, and then once a connection is established, the eNBmay transfer operation to another WS channel. In this implementation,the RACH procedure signaling may be provided on only one or a few of theWS channels used.

FIG. 9 illustrates another configuration 900, where multiple WStransmitters are used by an eNB 910, similar to that shown in FIG. 10.In this implementation, however, the licensed channel provides onlyinformation regarding which WS channel or channels are being used. Thisinformation may be provided in an IE in SIBs 1 or 2, for example. Uponreceipt of this information, a UE 920 may then transition operation toone or more of the available WS channels. In this case, the eNB willgenerally provide RACH procedure capability on multiple WS channels toallow connection with any of the channels, rather than a preferred orrequired channel as shown in FIG. 8.

In some cases, the UE 920 may have previously searched the available WSchannels and may have determined one or more preferable channels.Alternately or in addition, the UE may have detected an unusablechannel, such as, for example, a channel that is being used by a primaryuser (and it therefore restricted). If the UE has not done any previoussearching, it may proceed to acquisition of a particular WS channel or,in some cases, multiple WS channels if supported by the UE.

Once UE operation has been established, the UE may signal information tothe eNB regarding which channel or channels it has selected, and/orother information related to WS operation.

Attention is now directed to FIG. 10, which illustrates an embodiment ofa process 1000 for connection and WS operation. At stage 1010, aWS-enable UE, such as the UEs shown in FIGS. 1-5 and 8-9, search forcells on licensed spectrum. The initial search process may be done onlyon licensed spectrum, even if the UE is capable of performing similarsearching on WS channels. At stage 1020, the UE may receivesynchronization signals (e.g., PSS, SSS) and perform synchronizationoperations such as are described in, for example, the LTEspecifications. Once synchronized with a particular cell and associatedeNB, the UE may then receive broadcast information, which may beprovided in one or more SIBs such as described previously herein. Theassociated eNB may be WS enabled or may be a legacy eNB (i.e., not WSenabled). At decision stage 1040, a decision may be made based on theSIB information element(s). If no WS information is received, the UE mayproceed to stage 1050 where a legacy connection may be established.Alternately, if WS-specific information (such as, for example, WSchannelization and/or priorities) is received, the UE may proceed tostage 1060, where a search of WS channel or channels may be done. Thechannel search may be based on WS channel information provided in theSIB or SIBs received from the licensed channel. At stage 1070, asynchronization operation may be performed based on signaling (e.g.,PSS, SSS) received on a detected WS channel or channels. At stage 1080,broadcast information (such as, for example, MIB, SIB 1, or SIB2) may bereceived via a WS channel. Finally, at stage 1090, the UE may beginoperation on the WS channel. In particular, the UE may begin to receiveDL transmissions on the WS channel, and in some cases may also use a WSUL channel to communicate with the eNB.

In some implementations, WS-enabled eNBs may be in communication onlywith legacy UEs (i.e., no WS-enabled UEs are present). In this case,licensed channel signaling as described previously herein may also beused, with the additional requirement that the eNB support data trafficon the licensed DL channel, in addition to the control informationdescribed previously (e.g., synchronization and broadcast information).In addition, in some implementations legacy UEs (as well as WS-UEs) maybe operated in a network, such as a heterogeneous network (hetnet),which further includes resource partitioning functionality. In someimplementations, the resource partitioning functionality may betriggered only upon addition of a legacy UE. For example, if there isany interference coordination scheme (i.e., resource partitioning andinterference coordination techniques), the hetnet may be configuredbased solely on legacy users and not WS users (unless the WS users arealso impacting the licensed spectrum traffic).

An example of this is shown in FIG. 11, which illustrates a process 1100for transitioning operation of an eNB from WS-only operation. Similarprocedures may be used for addition of legacy UEs to a network alreadyincluding one or more legacy UEs. At stage 1110, it is assumed that aneNB is operating only with WS-UEs and may not be using any interferencecoordination. At stage 1120, a new UE may be added, and a decision as towhether the new UE is a legacy UE or WS-UE may be made. If the new UE isa WS-UE, processing may continue to stage 1110. Alternately, if a legacyUE is detected, the eNB may then establish a legacy connection at stage1130, such as solely through use of licensed channels. At stage 1140,the eNB may then initiate interference coordination with other adjacenteNBs, which may be done using L2 signaling. This may be done by using,for example, X2 and/or S1 connections with the adjacent eNBs which mayinclude information such as, for example, loading. Coordination may bedetermined by the eNB, by another eNB, in coordination between eNBs,and/or by a core network module. At stage 1160, the eNB may receivepartition configuration information and/or resource allocations. Thepartition information may be signaled to the legacy UE or UEs (such as,for example, semi-static allocations), and/or to the WS-UEs.

In addition, at stage 1140, L2 signaling may include signalinginformation associated with both the legacy UE(s) using licensedspectrum, as well as WS-UEs. This may be useful, for example, ifadjacent cells use the same WS, coordination of WS spectrum use may alsobe done. Moreover, in some cases, coordination of use of both licensedand WS spectrum may be done between two or more adjacent eNBs, which maybe of different classes and/or power levels.

Attention is now directed to FIG. 12, which illustrates an embodiment ofa corresponding process 1200 for reallocating resources upon terminationof a legacy UE connection in a WS-enabled cell. At stage 1210 it isassumed that a WS-enabled eNB in operating with both WS and legacy UEs,and interference coordination is being used, such as by use of resourcepartitioning. At stage 1220, a decision step may be performed to testfor disconnection of a legacy UE (such as by power off, handoff, orother event). If a legacy UE has terminated operation, a resourcereallocation request may be made at stage 1240. This may include sendingL2 information, such as via an X2 or S1 connection, to adjacent eNBs. Aresource reallocation may be negotiated or determined, and may bereceived at the eNB at stage 1250. If no legacy UEs remain, the eNB maywish to terminate resource partitioning. At stage 1260, updated resourcepartitioning information (such as, for example, semi-static subframeallocations) may be provided to any remaining legacy UEs. In addition,the information may also be provided to any WS-UEs.

Attention is now directed to FIG. 13, which illustrates a system 1300including a transmitter system 1310 (also known as the access point oreNB) and a receiver system 1350 (also known as access terminal or UE) inan LTE MIMO system 1300. At the transmitter system 1310, traffic datafor a number of data streams is provided from a data source 1312 to atransmit (TX) data processor 1314. Each data stream is transmitted overa respective transmit antenna. TX data processor 1314 formats, codes,and interleaves the traffic data for each data stream based on aparticular coding scheme selected for that data stream to provide codeddata.

The coded data for each data stream may be multiplexed with pilot datausing OFDM techniques. The pilot data is typically a known data patternthat is processed in a known manner and may be used at the receiversystem to estimate the channel response. The multiplexed pilot and codeddata for each data stream is then modulated (i.e., symbol mapped) basedon a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or M-QAM)selected for that data stream to provide modulation symbols. The datarate, coding, and modulation for each data stream may be determined byinstructions performed by processor 1330.

The modulation symbols for all data streams are then provided to a TXMIMO processor 1320, which may further process the modulation symbols(e.g., for OFDM). TX MIMO processor 1320 then provides NT modulationsymbol streams to NT transmitters (TMTR) 1322 a through 1322 t. Incertain embodiments, TX MIMO processor 1320 applies beam-forming weightsto the symbols of the data streams and to the antenna from which thesymbol is being transmitted.

Each transmitter 1322 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and up-converts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel. NTmodulated signals from transmitters 1322 a through 1322 t are thentransmitted from NT antennas 1324 a through 1324 t, respectively.

At receiver system 1350, the transmitted modulated signals are receivedby NR antennas 1352 a through 1352 r and the received signal from eachantenna 1352 is provided to a respective receiver (RCVR) 1354 a through1354 r. Each receiver 1354 conditions (e.g., filters, amplifies, anddown-converts) a respective received signal, digitizes the conditionedsignal to provide samples, and further processes the samples to providea corresponding “received” symbol stream.

An RX data processor 1360 then receives and processes the NR receivedsymbol streams from NR receivers 1354 based on a particular receiverprocessing technique to provide NT “detected” symbol streams. The RXdata processor 1360 then demodulates, de-interleaves, and decodes eachdetected symbol stream to recover the traffic data for the data stream.The processing by RX data processor 1360 is complementary to thatperformed by TX MIMO processor 1320 and TX data processor 1314 attransmitter system 1310.

A processor 1370 periodically determines which pre-coding matrix to use(discussed below). Processor 1370 formulates a reverse link messagecomprising a matrix index portion and a rank value portion. The reverselink message may comprise various types of information regarding thecommunication link and/or the received data stream. The reverse linkmessage is then processed by a TX data processor 1338, which alsoreceives traffic data for a number of data streams from a data source1336, modulated by a modulator 1380, conditioned by transmitters 1354 athrough 1354 r, and transmitted back to transmitter system 1310.

At transmitter system 1310, the modulated signals from receiver system1350 are received by antennas 1324, conditioned by receivers 1322,demodulated by a demodulator 1340, and processed by a RX data processor1342 to extract the reserve link message transmitted by the receiversystem 1350. Processor 1330 then determines which pre-coding matrix touse for determining the beam-forming weights then processes theextracted message.

DETERMINATION AND BROADCAST OF WHITE SPACE (WS) CHANNEL INFORMATION: Insome communication systems using licensed channels as well as unlicensedchannels, such as WS channels, it may be desirable to provideinformation regarding WS channel utilization between base station nodes,such as eNBs, as well as from base stations to user terminals, such asUEs.

For example, in some implementations, a wireless network, such as an LTEnetwork, may include a macrocell controlled by a macronode base station,such as a macro eNB. One or more additional nodes, such as, for example,low power nodes, may also be partially or fully within the coverage areaof the macronode (e.g., within a coverage umbrella of the macrocell).The low power nodes may be, for example, low power base stations oreNBs, such as femtocell nodes (femtonodes), picocell nodes (piconodes),and/or other lower power nodes. In addition, in some cases, the othernodes may also be macrocell nodes of the same or different power levels.For example, macronodes of various power classes may be deployed withinoverlapping coverage areas of a primary macronode. Although the variousembodiments described below are described with respect to a macrocellnode (e.g., macro base station or eNB) and one or more low power nodes(e.g., pico or femto base station or eNB), the techniques and apparatusmay also be used in configurations with macrocells of different typesand/or power levels. In a typical implementation, the macrocell basestation may be an eNB configured such as is shown in, for example, FIG.13.

In some embodiments, the macrocell node may be configured to transmitand receive signals from connected or served user terminals, such asUEs, only on licensed spectrum. However, in cognitive systems, the macroand/or additional low power nodes may be further configured to operateon both licensed spectrum and unlicensed spectrum, such as WS spectrumand associated WS channels. In a typical implementation, the licensedspectrum may be spectrum licensed for LTE operation, while theunlicensed spectrum may be WS spectrum, such as TV WS spectrum asdescribed previously herein. In one example implementation,approximately 40 WS channels may be available within the WS spectrum. Itwill, however, be apparent that other spectrum and channelconfigurations may be used in some implementations.

In implementations such as LTE systems, several basic broadcast signalsincluding cell-related information are periodically transmitted by abase station of each cell to allow user terminals, such as UEs, tolocate or discover the cell, measure cell signal characteristics anddetermine cell information, such as cell identification (cell ID), andpossibly access or camp on the cell.

WHITE SPACE (WS) PROCEDURES FOR LTE: In accordance with aspects of theembodiments described herein, there is provided a WS technique for LTEoperation of a mobile entity (e.g., a UE, access terminal, or the like)by storing the WS credentials as part of the UE subscriptioninformation.

In order to operate in WS, a network entity (e.g., an eNB or the like)and the mobile entity should perform certain procedures in order toauthorize operation in the WS spectrum based on local regulations. Thenetwork entity may perform the WS operation procedures before it startsadvertising service availability in the WS spectrum. The mobile entitymay perform the WS operation procedures in order to start using the WSspectrum for communication.

The technique described herein simplifies the authorization proceduresby storing the WS credentials of the mobile entity in the subscriptioninformation or the like for the mobile entity in the network, and bypassing it around to other network entities as the mobile entity ishanded over in the network.

It is noted that there may be two different types of devices operatingin the WS spectrum. A first type of device, referred to herein as a UEeNodeB (UeNB) may be a device that advertises its availability as an eNBin a whitespace spectrum and may provide network connectivity for otherUEs. A UeNB may have a wireless backhaul including LTE in licensedspectrum, or a wired backhaul. A second type of device, referred toherein as a terminal UE (TUE), may be a UE connecting to the network viathe UeNB for service in a whitespace spectrum.

With reference to the example of FIG. 14A, there is shown a UeNB 1404providing network access via a wireless link 1406 to a terminal UE 1408,wherein UeNB-1 has a wired backhaul 1402 to the network 1410. FIG. 14Bshows a UeNB 1416 providing wireless access over link 1418 to a terminalUE 1420, wherein the UeNB 1416 is being served via wireless link 1414 byan eNB 1412 that uses an LTE backhaul or the like (not shown). In bothof these examples, a given UeNB may provide network connectivity to aterminal UE over a wired backhaul and/or an LTE backhaul.

In related aspects, while a UeNB is active, it may: communicate with its(potentially) served terminal UEs on the access; and, for a relay,communicate with its serving eNB on the backhaul. On the backhaul-hop,the UeNB may behave essentially like a UE, from the PHY-MAC perspective.During periods of low traffic activity, the UeNB may go intodiscontinuous reception (DRX) or idle mode on the backhaul hop forpower-saving or network-load-alleviation. On the access-hop, the UeNBmay behave essentially like a cell, from the PHY-MAC perspective. TheUeNB may incorporate additional power-savings techniques as compared toa regular eNB or network-relay.

ARCHITECTURE REFERENCE MODEL: With reference to FIG. 15, there is showna general architecture reference model 1500 for a UeNB 1502 servicing aterminal 1520. The data plane terminates at the eNB function 1504 forthe UeNB, thereby bypassing the UeNB Core Network (CN) 1508 controlplane to provide access to a Wide Area Network 1510 (e.g., the Internet)via a local gateway (LGW) 1506. For example, the architecture definedfor Local IP access (LIPA) or Selective IP Traffic Offload (SIPTO) inRel-10, or variations thereof, may be employed. The Home enhancedManagement System (HeMS) 1512 (Operations, Administration, & Maintenance(OAM)) may reuse TR-069 as defined for the Home enhanced Node B (HeNB)1504, or variations thereof. The control plane may be centralized usingthe Mobility Management Entity (MME) 1514/Serving Gateway (SGW) 1516 andHome Subscriber Server (HSS) 1518, such that changes to existingprotocols are not needed and the whitespace procedures may be supportedupon implementation of the above described general architecture.

With reference to FIG. 16, there is shown a general architecturereference model 1600 for a UeNB 1602 (including eNB 1604, LGW 1606 andUE 1607) with an LTE backhaul 1622 (i.e., a UeNB acting as a relay)including eNB 1624, SGW 1626 and PGW 1628. For the WS backhaul, abaseline UeNB 1622 provides the access to Wide Area Network 1610 forterminal 1620. For WS access, a baseline UeNB 1622 may provide any typeof backhaul. Such a protocol may run over the top of various networks,for example, legacy cellular network, wired, or Wi-Fi. The UeNB/DonoreNB (DeNB) core network 1608 may include the HeMS node 1612, SGW 1516,MME 1614 and HSS 1618, similarly to model 1500.

UeNB SETUP FOR WS BACKHAUL: With reference to FIG. 17, there is shown anexample call flow 1700 for UeNB 7102 setup for the WS backhaul. Otherentities in the call flow 1700 include the donor eNB 1704, MME 1706,SGW/PGW 1708, HHS 1710, OAM 1712, MME 1718 and WS database (WSDB) 1720.The setup may include WS procedures 1722, 1728 and channel selection1724. Further aspects of the setup 1700 may include: authorization toestablish a connection by the UeNB 1726 as defined in 3GPP for a UE inTS 23.401, for example, authorizing a relay operation or other servicerequest; OAM configuration 1730 as defined in 3GPP for a eNB in TS32.593; and CN control plane setup 1732 as defined in 3GPP for a eNB inTS 36.413. After establishing the control plane connection to the MME,the UeNB 1702 operates as a relay on WS bandwidth 1734.

More specifically, with continued reference to FIG. 17, at 1722, theDonor eNB (DeNB) 1704 may be authorized as a master white space device(WSD) for use of the WS. At 1724, the DeNB may perform WS channelselection. At 1726, the UeNB may establish backhaul connectivity on theWS channel and authorization for operating as a relay UE. At 1728, theUeNB may be authorized as a slave WSD for use of the whitespace. At1730, the UeNB may retrieve configuration parameters via the OAM. At1732, the UeNB may establish a control plane connection to the MME usingS1 and S5 setup procedures. The UeNB may then, at 1734, operate as arelay UE on WS bandwidth.

UeNB SETUP FOR WS ACCESS: With reference to FIG. 18, there is shown anexample call flow 1800 for UeNB setup for WS access. Entitiesparticipating in the call flow may include a terminal UE 1814, UeNB1802, DeNB 1804, DeNB core network 1806, OAM 1808, MME 1810 and WSDB1812. The setup may include, at 1816, authorization to establish aconnection by the UeNB, as defined in 3GPP for a UE in TS 23.401 (e.g.,service request). In related aspects, the setup may include, at 1818,OAM configuration, as defined in 3GPP for a eNB in TS 32.593. In furtherrelated aspects, the setup may include WS procedures at 1820, 1830 andchannel selection at 1822. In yet further related aspects, the setup mayinclude, at 1824, the CN control plane setup, as defined in 3GPP for aeNB in TS 36.413. In still further related aspects, the setup mayinclude, at 1828, authorization to establish a connection by the UE, asdefined in 3GPP for a UE in TS 23.401 (e.g., service request).

WS OPERATION: With reference to FIG. 19, there is shown a generalarchitecture reference model 1900 for WS operations. When the WS is usedfor access, the master WS function is in the eNB function of the UeNB,and the slave WS function is in the Terminal UE. When the WS is used forbackhaul, the master WS function is in the DeNB, and the slave WSfunction is in the UE function of the UeNB. WS operation procedures maybe performed by both an eNB function and a UE function in order toauthorize operation in the WS spectrum based on local regulations.

In related aspects, the eNB may perform the WS operation procedures (seeMASTER WSD TO WSDB COMMUNICATIONS, explained in further detail below)before it starts advertising service availability in the WS spectrum. Infurther related aspects, the UE may perform the WS operation procedures(see SLAVE WSD TO MASTER WSD COMMUNICATIONS, explained in further detailbelow) in order to start using the WS spectrum for communication.

With continued reference to FIG. 19, the WS network elements 1900 mayinclude a master WSD 1904, 1910, which is a device that consults a WSdatabase 1906 in order to obtain a list of available WS channels at thedevice's location, and corresponding RF parameters in each availablechannel, e.g., EIRP. It is noted that, for WS access, the master WSD isa UeNB 1910. For WS backhaul the master WSD is the DeNB 1904. In furtherrelated aspects, the WS network elements also include a slave WSD 1902,1908, which is a device that does not directly communicate with a WSdatabase but is under the control of a master WSD. It is noted that, forWS access, the slave WSD is a terminal UE 1908, whereas, for WSbackhaul, the slave WSD is the UeNB 1902. In further related aspects,the WS network elements also include a WS database (WSDB) 1906, which isa device that communicates to a master WSD a location-specific list ofavailable WS channels, and corresponding RF parameters in each availablechannel, e.g., EIRP.

MASTER WSD TO WSDB COMMUNICATIONS: The master WSD may be authenticatedby sending identification parameters (e.g., FCC ID or the like) to theWSDB in order to receive a list of available WS channels to operate inthe WS. For example, the identification parameters may include an IDthat is defined for and unique to the device and is related to WSoperation based on location regulations or the like. In one approach,the master WSD may contact the WSDB in the following instances: (a) whenthe master WSD initially starts up or attaches to a network; (b) whenthe master WSD detects that its location has changed sufficiently thatit is outside the boundary defined for the list of available WS channelscurrently in use; and/or (c) when the current list of available WSchannels has expired.

Certain procedures may be defined for master WSD to WSDB communications,such as, for example, WSDB discovery (since the master WSD should findthe relevant WSDB based on its current location or for another location)and WSDB access (since the master WSD should securely access therelevant WSDB to be authenticated and receive the list of available WSchannels).

With respect to WSDB discovery, the spectrum and databases are countryspecific since the available spectrum and regulations vary from countryto country. Thus, the master WSD will need to discover the relevantdatabase based on location. The master WSD should obtain the IP addressof the specific WSDB to which it can send queries in addition toauthenticating itself for operation and using the available spectrum.The master WSD may be pre-configured with the IP address of a trustedWSDB. In the alternative, or in addition, the master WSD may use theWSDB discovery procedures to find a trusted WSDB at the currentlocation.

The WSDB discovery procedures are expected to be along the followinglines of the following. The master WSD may initiate a process to get theIP address of WSDB by forming a fully qualified domain name (FQDN) forthe WSDB. The FQDN may be pre-programmed in the master WSD at thefactory, may be configured by OAM, or may be formed based on otherdefined rules. The master WSD may perform DNS query to a public DNS withthe FQDN. The DNS may respond to the HeNB with the IP address of theWSDB. It is noted that in order to perform the discovery procedures themaster WSD may need to first establish IP connectivity via an approachother than using the WS radio.

With respect to WSDB access, the master WSD should securely access therelevant WSDB to be authenticated for WS operation and receive the listof available WS channels. As part of the access procedure, the masterWSD may provide identification, geo-location and any other informationrequired by local regulation. The WSDB access should protect both thechannel enablement process and the privacy of users including preventionof device identity spoofing, modification of device requests,modification of channel enablement information, impersonation ofregistered database services, or unauthorized disclosure of a device'slocation.

SLAVE WSD TO MASTER WSD COMMUNICATIONS: The slave WSD should beconfigured to exchange parameters and identification information withthe master WSD to operate in WS. Certain procedures may be defined forslave WSD to master WSD communications, such as, for example, WSenablement and WS authorization.

With respect to WS enablement, the master WSD may transmit a WS enablingsignal that indicates to a slave WSD that it is capable of enabling WSoperations for a slave WSD. The slave WSD may requests authorizationfrom the master WSD that transmits the WS enabling signal to operate inthe WS. For example, with reference to FIG. 20 (a first embodiment of WSenablement), there is shown a call flow 2000 for WS initialauthorization of the slave WSD 2002 by the master WSD 2004, wherein theUE's WS credentials are stored as part of the subscription informationaccessed via an MME 2006.

With continued reference to the first embodiment of WS enablement shownin FIG. 20, at 2008, the master WSD may transmit a WS enabling signalthat indicates to a slave WSD 2002 that it is capable of enabling WSoperations for a slave WSD. For example, the WS enabling signal may be asingle bit IE sent in SIB1 or the MIB and may need to be received by theslave WSD before it is allowed to transmit in the WS. In the case of FDDoperation, the master WSD 2004 should broadcast the appropriate ULchannel, for the UE to use to initiate the RACH procedure. The slave WSDmay receive the broadcast WS enablement signal from the master WSD inorder to initiate the WS enablement procedures at 2008, for example. Atsteps 2010-2020, the slave WSD 2002 may perform the normal connectionsetup procedures with the master WSD and may be authenticated by the MMEor the like for service.

At 2022, the MME may include the Slave WS parameters in the S1 InitialContext Setup Request message or the like as part of the UE's context.The slave WS parameters may include an FCC ID or the like that allowsthe master WSD 2004 to verify that the slave WSD 2002 is eligible forservice. At 2024, the master WSD 2004 may accept/reject the slave WSD2002 using an RRCConnectionConfiguration message or the like. If themaster WSD accepts the slave WSD, the slave WSD is enabled for WSoperation; otherwise the connection is RRC released.

The RRCConnectionConfiguration message may include a WS Map (WSM) thatincludes a list of identified available channels, the correspondingmaximum allowed transmission powers for each available channel and anexpiry timer. The WSM facilitates an efficient channel search since theUE only needs to search those channels listed as part of the WSM. It isnoted that the WSM may be sent securely using RRC security. It is alsonoted that the slave WSD generally transmits on channels identified bythe WSM as available for WS operation. It is further noted that themacrocell may, based on local regulations, also advertise a list ofavailable WS frequencies which can be used to improve the searchefficiency of the UE. In the alternative, or in addition, the UE may beconfigured for each region on the available WS frequencies. The WSMreceived by the master WSD may take precedence for actual WS operation.

In response to the slave WSD having previously been authorized by themaster WSD, e.g., due to connection re-establishment due to RLF or thelike, the RRCConnectionConfiguration message or the like may include amap index to identify a WSM that was sent previously. If the map indexis different from the last received map index, the slave WSD may requesta new WSM, such as, for example, by setting a field in theRRCWSConfigurationRequest message 2014 or the like. It is noted that,for 802.11af, there may be an additional set of optimizations to managethe WSM by identifying the WSM with an index and enabling partialupdating of the list, and similar procedures may be defined for LTE. Itis also noted that the WS authorization may need to be periodicallyrepeated by the slave WSD based on an expiry timer in theRRCWSConfiguration message or the like. It is further noted that the WSauthorization is generally accepted by the UeNB after the UE isauthenticated by the MME.

With reference to FIG. 21 (a second embodiment of WS enablement), thereis shown a call flow 2100 for WS initial authorization of the slave WSD2102 by the master WSD 2104 in connection with an MME 2106 and WSDB2107, wherein the UE provides the WS credentials in RRC message(s). At2108, the master WSD may transmit a WS enabling signal that indicates toa slave WSD that it is capable of enabling WS operations for a slaveWSD, as described above with respect to the analogous 2008 in FIG. 20.Referring once again to FIG. 21, at 2110-2124, the slave WSD 2102 mayperform the normal connection setup procedures with the master WSD andmay be authenticated by the MME or the like for service.

At 2126, the slave WSD 2102 may request authorization for use of the WSby the master WSD using the RRCWSConfigurationRequest message or thelike. In the alternative, the RRCWSConfigurationRequest message is notutilized; rather, the MME may includes the relevant information for WSauthorization in the subscription information of the slave WSD in the S1Initial Context Setup Request or the like. Similarly for HO, the slaveWSD may request authorization using the RRCWSConfigurationRequestmessage or the information needed for authorization is included in theHO request received at the target eNB.

At 2128-2130, based on local regulations, the master WSD 2104 may verifythat the slave WSD 2102 is authorized for WS operation with the WSDB. At2132, the master WSD 2104 may accept/reject the slave WSD 2102 using theRRCWSConfiguration message 2132 or the like, as described above withrespect to the analogous 2024 in FIG. 20. Referring once again to FIG.21, at 2134, the slave WSD 2102 may optionally respond with anRRCWSConfigurationComplete message or the like. It is also noted thatthe RRCWSConfigurationRequest or the like may alternatively be sent in2118, and that the RRCWSConfiguration or the like may alternatively besent in 2124.

With respect to WS authorization, the master WSD may transmits a secureWS enabling signal to the slave WSD to allow it to continue to operatein the WS. In certain geographic regions (e.g., the US), the master WSDshould periodically send a message to the slave WSD to verify that it isstill within reception range and to validate the available channel list(in the WSM). It is noted that the IE used for this purpose may bereferred to as the contact verification signal (CVS), e.g., in FCCregulations and also in 802.11af, and may be sent from the master WSD tothe slave WSD periodically (e.g., at least once per minute based on FCCregulations). The CVS should be sent securely and the slave shouldreceive the CVS from the master that enabled it. If the slave does notreceive a CVS at the defined time interval (e.g., every 60 seconds) itshould start over and request enablement from the original master oranother master.

With reference to the example of FIG. 22, there is shown a call flow2200 for WS continued authorization of the slave WSD 2202 by the masterWSD 2204, involving the sending the CVS in RRC. At 2206, the master WSDsends the slave WSD an RRCWS configuration message including the CVS IE.Optionally, the slave WSD 2202 responds at 2208 with an RRCWSreconfiguration complete message. It is noted that, for LTE, since theCVS IE should be sent securely and the slave should receive the CVS IEevery 60 second, it makes sense for the UE to perform the WS initialauthorization when it transitions from idle to connected mode. Afterthat, the UE may use the WS continued authorization procedure tocontinue to operate. Such an approach would be preferable over pagingthe UE to send the CVS IE.

In view of example systems shown and described herein, methodologiesthat may be implemented in accordance with the disclosed subject matter,will be better appreciated with reference to various flow charts. While,for purposes of simplicity of explanation, methodologies are shown anddescribed as a series of acts/blocks, it is to be understood andappreciated that the claimed subject matter is not limited by the numberor order of blocks, as some blocks may occur in different orders and/orat substantially the same time with other blocks from what is depictedand described herein. Moreover, not all illustrated blocks may berequired to implement methodologies described herein. It is to beappreciated that functionality associated with blocks may be implementedby software, hardware, a combination thereof or any other suitable means(e.g., device, system, process, or component). Additionally, it shouldbe further appreciated that methodologies disclosed throughout thisspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methodologies tovarious devices. Those skilled in the art will understand and appreciatethat a methodology could alternatively be represented as a series ofinterrelated states or events, such as in a state diagram.

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 23, there is shown a master WSD setupmethodology 2300, operable by an access point (e.g., UeNB or the like).Specifically, the method 2300 may involve, at 2310, the access pointreceiving, from a core network entity (e.g., OAM), configurationparameters to operate as a base station (e.g., eNB) using at least onenon-WS bandwidth. The method 2300 may involve, at 2320, determiningwhether the received configuration parameters include an indication forthe network entity to use WS for the service. The method 2300 mayinvolve, at 2330, requesting authorization information from a WSdatabase to operate in the WS, in response to the received parameterscomprising the indication.

In related aspects, requesting (block 2330) may involve requesting tooperate as a master WSD. In the alternative, requesting (block 2330) mayinvolve requesting to operate as a slave WSD. In yet further relatedaspects, the indication (block 2320) may be, or may include an IEindicating that the network entity should use the WS. The indication(block 2320) may be/include a list of bands for the operation, the listcomprising a WS band.

In further related aspects, with reference to FIG. 24, the method 2300may include additional operations 2400. For example, the method 2300 mayfurther involve, at 2410, authorizing a slave WSD (e.g., terminal UE)for use of the WS. The method 2300 may further involve, at 2420,selecting a WS channel based on at least one of the configurationparameters and the authorization information, and establishing backhaulconnectivity on the WS channel.

In accordance with one or more aspects of the embodiments describedherein, there are provided devices and apparatuses for master WSD setup,as described above with reference to FIG. 23. With reference to FIG. 25,there is provided an example apparatus 2500 that may be configured as aUeNB or the like, or as a processor or similar device/component for usewithin. The apparatus 2500 may include functional blocks that canrepresent functions implemented by a processor, software, or combinationthereof (e.g., firmware). For example, apparatus 2500 may include anelectrical component or module 2512 for receiving configurationparameters to operate as a base station from a core network entity. Theapparatus 2500 may include a component 2514 for determining whether thereceived configuration parameters include an indication for the networkentity to use WS for the service. The apparatus 2500 may include acomponent 2516 for requesting authorization information from a WSdatabase to operate in the WS, in response to the received parameterscomprising the indication.

The components 2512-2516 may comprise means for performing the describedfunctions. More detailed algorithms for accomplishing the describedfunctions is provided herein above, for example, in connection withFIGS. 17-22.

In related aspects, the apparatus 2500 may optionally include aprocessor component 2550 having at least one processor, in the case ofthe apparatus 2500 configured as a network entity (e.g., an eNB), ratherthan as a processor. The processor 2550, in such case, may be inoperative communication with the components 2512-2516 via a bus 2552 orsimilar communication coupling. The processor 2550 may effect initiationand scheduling of the processes or functions performed by electricalcomponents 2512-2516.

In further related aspects, the apparatus 2500 may include a transceivercomponent 2554 (radio/wireless or wired). A stand alone receiver and/orstand alone transmitter may be used in lieu of or in conjunction withthe transceiver 2554. When the apparatus 2500 is a network entity,service authentication entity, a core network entity, or the like, theapparatus 2500 may also include a network interface (not shown) forconnecting to one or more network entities. The apparatus 2500 mayoptionally include a component for storing information, such as, forexample, a memory device/component 2556. The computer readable medium orthe memory component 2556 may be operatively coupled to the othercomponents of the apparatus 2500 via the bus 2552 or the like. Thememory component 2556 may be adapted to store computer readableinstructions and data for effecting the processes and behavior of thecomponents 2512-2516, and subcomponents thereof, or the processor 2550,or the methods disclosed herein. The memory component 2556 may retaininstructions for executing functions associated with the components2512-2516. While shown as being external to the memory 2556, it is to beunderstood that the components 2512-2516 can exist within the memory2556. It is further noted that the components in FIG. 25 may comprisevarious components, for example, processors, electronic devices,hardware devices, electronic sub-components, logical circuits, memories,software codes, firmware codes, or any combination thereof.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, circuits, and process steps described inconnection with the disclosure herein may be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present disclosure.

The various illustrative logical blocks, modules, and circuits describedin connection with the disclosure herein may be implemented or performedwith a general-purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or process described in connection with thedisclosure herein may be embodied directly in hardware, in a softwaremodule executed by a processor, or in a combination of the two. Asoftware module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. An examplestorage medium is coupled to the processor such that the processor canread information from, and write information to, the storage medium. Inthe alternative, the storage medium may be integral to the processor.The processor and the storage medium may reside in an ASIC. The ASIC mayreside in a user terminal. In the alternative, the processor and thestorage medium may reside as discrete components in a user terminal.

In one or more example designs, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage medium is a type of a non-transitory medium and may include anyavailable storage medium that can be accessed by a general purpose orspecial purpose computer. By way of example, and not limitation, suchcomputer-readable media can include RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code means in the form of instructions or data structures andthat can be accessed by a general-purpose or special-purpose computer,or a general-purpose or special-purpose processor. Disk and disc, asused herein, includes compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk and blu-ray disc. Combinationsof the above should also be included within the scope ofcomputer-readable media.

The previous description of the disclosure is provided to enable anyperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Thus, the disclosure is not intended to be limited tothe examples and designs described herein but is to be accorded thewidest scope consistent with the principles and novel features disclosedherein.

What is claimed is:
 1. A method operable by an access point for wirelesscommunication service, the method comprising: receiving configurationparameters, from a core network entity, for the access point to operateas a base station using at least one non-white space (non-WS) bandwidth,the configuration parameters including a set of one or more bandwidthsthat may be used by the access point to facilitate the wirelesscommunication service; determining whether the set of one or morebandwidths includes at least a first white space (WS) bandwidth for theaccess point to use WS for the wireless communication service; and inresponse to a determination that the set of one or more bandwidthsincludes at least the first WS bandwidth, transmitting a request to a WSdatabase for requesting authorization information to operate in the WSusing the first WS bandwidth, the request including the first whitespace bandwidth.
 2. The method of claim 1, wherein the request for theauthorization information comprises requesting to operate as a master WSdevice (WSD).
 3. The method of claim 1, wherein the request for theauthorization information comprises requesting to operate as a slave WSdevice (WSD).
 4. The method of claim 1, wherein the configurationparameters further comprise an indication to use the WS for a backhaulor an access connectivity.
 5. The method of claim 4, wherein the requestfor authorization information comprises requesting to operate as a slaveWS device (WSD) in response to the indication to use the WS for thebackhaul connectivity.
 6. The method of claim 4, wherein the request forthe authorization information comprises requesting to operate as amaster WS device (WSD) in response to the indication to use the WS forthe access connectivity.
 7. The method of claim 1, further comprisingauthorizing another access point to operate as a slave WSD for use ofthe WS.
 8. The method of claim 1, further comprising establishing abackhaul connectivity on the first WS bandwidth.
 9. An access point forwireless communication service, the access point comprising: means forreceiving configuration parameters, from a core network entity, for theaccess point to operate as a base station using at least one non-whitespace (non-WS) bandwidth, the configuration parameters including a setof one or more bandwidths that may be used by the access point tofacilitate the wireless communication service; means for determiningwhether the set of one or more bandwidths includes at least a firstwhite space (WS) bandwidth for the access point to use WS for thewireless communication service; and means for transmitting a request toa WS database for authorization information to operate in the WS usingthe WS in response to a determination that the set of one or morebandwidths includes at least the WS, the request including the firstwhite space bandwidth.
 10. An access point for wireless communicationservice, the access point comprising: at least one processor configuredto: receive configuration parameters, from a core network entity, forthe access point to operate as a base station using at least onenon-white space (non-WS) bandwidth, the configuration parametersincluding a set of one or more bandwidths that may be used by the accesspoint to facilitate the wireless communication service; determinewhether the set of one or more bandwidths includes at least a firstwhite space (WS) bandwidth for the access point to use WS for thewireless communication service; and in response to a determination thatthe set of one or more bandwidths includes at least the WS, transmit arequest to a WS database for request authorization information tooperate in the WS using the WS, the request including the first whitespace bandwidth; and a memory coupled to the at least one processor forstoring data.
 11. The access point of claim 10, wherein the processor isfurther configured to request to operate as a master WS device (WSD).12. The access point of claim 10, wherein the processor is furtherconfigured to request to operate as a slave WS device (WSD).
 13. Theaccess point of claim 10, wherein the configuration parameters comprisean indication to use the WS for a backhaul or an access connectivity.14. The access point of claim 13, wherein the processor is furtherconfigured to request to operate as a slave WS device (WSD) in responseto the indication to use the WS for the backhaul connectivity.
 15. Theaccess point of claim 13, wherein the processor is further configured torequest to operate as a master WS device (WSD) in response to theindication to use the WS for the access connectivity.
 16. The accesspoint of claim 10, wherein the processor is further configured toauthorize another access point to operate as a slave WSD for use of theWS.
 17. The access point of claim 10, wherein the processor is furtherconfigured to establish a backhaul connectivity on the first WSbandwidth.
 18. A computer program product, comprising: a non-transitorycomputer-readable medium comprising code for causing an access point forwireless communication service to: receive configuration parameters,from a core network entity, for the access point to operate as a basestation using at least one non-white space (non-WS) bandwidth, theconfiguration parameters including a set of one or more bandwidths thatmay be used by the access point to facilitate the wireless communicationservice; determine whether the set of one or more bandwidths includes atleast a first white space (WS) bandwidth for the access point to use WSfor the wireless communication service; and in response to adetermination that the set of one or more bandwidths includes at leastthe WS, transmit a request to a WS database for request authorizationinformation to operate in the WS using the WS, the request including thefirst white space bandwidth.